Skip to content

[AAASM-3695] 📝 (docs): Pin LlamaIndex example to released agent-assembly>=0.0.1b4#176

Closed
Chisanan232 wants to merge 1 commit into
masterfrom
v0.0.1/AAASM-3695/llamaindex_pin
Closed

[AAASM-3695] 📝 (docs): Pin LlamaIndex example to released agent-assembly>=0.0.1b4#176
Chisanan232 wants to merge 1 commit into
masterfrom
v0.0.1/AAASM-3695/llamaindex_pin

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

Description

The LlamaIndex example's Dependencies table pinned agent-assembly>=0.0.1b5 and labeled it "the release that ships the LlamaIndex adapter." But the adapter (agent_assembly/adapters/llamaindex/, exporting LlamaIndexAdapter) is already present at the current published version 0.0.1b4 (pyproject.toml version = "0.0.1b4"). 0.0.1b5 is unreleased, so a reader copying the pin gets an install failure. This changes the pin to agent-assembly>=0.0.1b4.

Type of Change

  • 🔧 Bug fix
  • 📚 Documentation update

Breaking Changes

  • No

Related Issues

  • Related JIRA ticket: AAASM-3695

Testing

  • No tests required (explain why)

Docs-only change. Verified against remote/master (HEAD 5639440): pyproject.toml version is 0.0.1b4, and agent_assembly/adapters/llamaindex/__init__.py exports LlamaIndexAdapter. Other example pins (b4/a2/b2) are valid lower bounds and were left untouched.

Checklist

  • Code follows project style guidelines
  • Self-review completed
  • Documentation updated if needed

🤖 Generated with Claude Code

The LlamaIndex adapter ships in the published 0.0.1b4 release, not the
unreleased 0.0.1b5. Pinning >=0.0.1b5 caused a copy-paste install
failure.
@Chisanan232

Copy link
Copy Markdown
Contributor Author

✅ Claude Code review — AAASM-3695

CI: all green — Analyze (python) ✅, Build documentation (PR, no deploy) ✅.

Scope vs ticket: docs/examples/llamaindex-tool-policy.md Dependencies pin agent-assembly>=0.0.1b5 (unreleased) → >=0.0.1b4. Verified the LlamaIndex adapter (agent_assembly/adapters/llamaindex/, exporting LlamaIndexAdapter) already ships at the published 0.0.1b4 (pyproject.toml), so a reader copying the pin now installs successfully. Other example pins (b4/a2/b2) untouched. AC fully met.

Verdict: ✅ Ready to approve & merge.

@Chisanan232

Copy link
Copy Markdown
Contributor Author

❌ Closing as not-a-bug (Claude Code, after owner review)

On deeper verification this is not a defect — the agent-assembly>=0.0.1b5 pin is a correct forward-reference, and this PR's downgrade to >=0.0.1b4 would actually break installs.

Evidence:

  • The LlamaIndex adapter (agent_assembly/adapters/llamaindex/) is absent from the published v0.0.1-beta.4 tag — it was added in commit 330e78a, after b4. master is 94 commits ahead but its version string was never bumped past b4.
  • master has 12 framework adapters; published b4 has only 7. The 5 new/unreleased ones — llamaindex, agno, haystack, microsoft_agent_framework, smolagents — are not on PyPI yet.
  • So pip install "agent-assembly>=0.0.1b4" installs the published b4, which does not contain LlamaIndexAdapterImportError. The example correctly tells readers they need the next release (b5).

Disposition: the doc is correct as-is; this PR is closed unmerged. AAASM-3695 will be satisfied by the upcoming python-sdk b5 release (which ships the 5 new adapters), not by editing the doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant